Systems and Methods for Discovering Lookalike Mobile Devices

ABSTRACT

The present disclosure provides methods and systems that utilize mobile device location events and machine learning and generate predicative classification/regression model for lookalike prediction. Location related features, together with other user level information, are extracted, transformed and used as model feature input, and a client specified list of mobile devices or their associated users are used as prediction target. This system makes efficient use of different types of location events and thus offers improved scale and performance. It also enjoys many benefits offered by a machine learning platform, such as automatic adaptation to different lists of seed lists, addition of new features and changes in data statistical properties.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 16/157,010, filed on Oct. 10, 2018 entitled “Systems and Methods for Using Geo-Blocks and Geo-Fences to Discover Lookalike Mobile Devices,” which is a non-provisional of U.S. Provisional Application No. 62/570,562, filed Oct. 10, 2017, entitled “System and Method for Discovering Lookalike Mobile Devices,” and a continuation-in-part of U.S. patent application Ser. No. 15/999,330, entitled “Systems and Methods for Using Geo-Blocks and Geo-Fences to Predict Mobile Device Locations,” filed Aug. 17, 2018, which is a continuation-in-part of U.S. patent application Ser. No. 15/344,482, filed Nov. 4, 2016, which claims priority to U.S. Provisional Application No. 62/251,090, filed Nov. 4, 2015, entitled “Systems and Methods for Creating and Using Geo-Blocks.” The present application is related to the patent application Ser. No. 15/999,331 entitled “System and Method for Real-Time Prediction of Mobile Device Locations,” filed Aug. 17, 2018. Each of the above-referenced applications is incorporated herein by reference in its entirety.

FIELD

The present disclosure is related to location-based information technologies, and more particularly to a system and method for machine learning to predict probabilities of mobile devices having lookalike characteristics with respect to a specified group of mobile devices.

DESCRIPTION OF RELATED ART

In modern society, smart mobile devices have become an integral part of people's daily life. Consequently, real time mobile device locations are becoming more commonly available to mobile service providers. It is of great interest to many service providers to utilize the location history information to discover mobile device users (lookalike users) that are similar to a given list of users (seed users), who can be, for example, existing users of a specific mobile app or users who have responded positively or negatively to a specific product feature. Lookalike users can be used by service providers to customize their services to individual users, recommend services new to individual users, and devise more cost effective advertising strategies to grow their customer bases. Moreover, the same technology can be applied to find lookalike users from seed users provided by other businesses and help them to achieve similar optimizations.

Lookalike modeling using location history at industrial scale face many challenges. Due to privacy concerns, third party access to location information is limited. Some common data sources include individual mobile apps, to which user explicitly grant access for data collection, and mobile advertising exchanges, which collect advertisement (ad) requests from a large collection of mobile apps. In the former case, it is common for device location to be collected only when the user is engaging with the mobile app. In the latter case, location data is collected only when an ad request is issued. As a result, collected device location history is often in the form of highly sporadic bursts of high frequency samples separated by long offline periods. As a result, location based models often work with extremely sparse user level location data, limited in both scale and performance. Some existing systems mitigate data sparsity by collecting data from a set of volunteering or payed users who are willing to provide densely sampled location history, and developing models for selecting lookalike mobile users based only on data collected from these users. A major drawback of this approach is its difficulty to ensure that the selected users are representative of a larger population, to which the developed model will be applied, because the number of volunteers is usually small and it is difficult to enforce control on user selection process. Some other systems rely on explicitly constructing a set of rules that encode prior knowledge about the seed users in order to more effectively extract information from the sparse data. This approach is limited in its scalability primarily because the rule finding process often requires extensive human involvement. Moreover, the rule finding process need to be repeated every time when a client provides a different list of seed users, when new types of user behavior data become available, or when the statistical property of user behavior data changes.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic representation of a system for discovering lookalike mobile devices according to certain embodiments.

FIG. 2 is a diagrammatic representation of a packet-based network according to embodiments.

FIG. 3 is a diagrammatic representation of a computer/server coupled to the packet-based network that performs one or more of the methodologies and/or to provide part or all of a system for location prediction according to embodiments.

FIG. 4 is a map image illustrating exemplary polygonal geo-fences overlaid on a map of a geographical region according to certain embodiments.

FIG. 5 is a table illustrating some of the content in a geo-fence database according to certain embodiments.

FIG. 6 is map a image illustrating exemplary geo-blocks overlaid on a map of a geographical region according to certain embodiments.

FIG. 7 is a table illustrating some of the content in a geo-block database according to certain embodiments.

FIGS. 8A-8C are block diagrams illustrating request data at different stages of processing according to certain embodiments.

FIG. 9 is a table illustrating some of the content in a request log according to certain embodiments.

FIG. 10 is a table illustrating some of the content in a feedback log according to certain embodiments.

FIG. 11 is a flowchart illustrating a method performed in a system for discovering lookalike mobile devices according to certain embodiments.

FIG. 12 is a diagram illustrating various mobile user partitions according to certain embodiments.

FIG. 13 is a block diagram illustrating a data manager for extracting mobile device data according to certain embodiments.

FIG. 14 includes tables illustrating extracted mobile device data corresponding to a time period according to certain embodiments.

FIG. 15 is a flowchart illustrating a method for building a feature space according to certain embodiments.

FIG. 16 is a table illustrating assigning geo-blocks to geo-block brackets based on relevance measures according to certain embodiments.

FIG. 17 includes tables of exemplary features associated with a mobile device according to certain embodiments.

FIG. 18 are tables illustrating a plurality of sets of labels corresponding to respective seed lists according to certain embodiments.

FIG. 19 is a table illustrating evaluation of a prediction model according to certain embodiments.

FIG. 20 is a table illustrating exemplary lookalike prediction results according to certain embodiments.

FIG. 21 is a table illustrating ranking of mobile users and selecting lookalike mobile users based on prediction results according to certain embodiments.

FIG. 22 is diagrammatic representation of an information server system provided using one or more computer/server systems according to certain embodiments.

FIG. 23 is a flowchart illustrating an information process performed by the information server system according to certain embodiments.

FIG. 24 is a diagrammatic representation of a geo-block definition subsystem provided by one or more computers/servers according to certain embodiments.

FIG. 25 is a flowchart illustrating a method performed by the geo-block definition system according to certain embodiments.

FIG. 26 is a flowchart illustrating a method for forming polygons outlining initial geo-blocks according to certain embodiments.

FIG. 27 is a flowchart illustrating a method for processing and logging real-time inputs (e.g., ad requests) with respect to initial geo-blocks according to certain embodiments.

FIG. 28 is a table illustrating a request log according to certain embodiments.

FIG. 29 is a map overlay diagram of geo-blocks illustrating separation of residential areas (enclosed by blue polygons) and a forest area by investigating spatial distribution of 9-digit zip codes.

FIG. 30 is a map overlay diagram of geo-blocks illustrating separation of an elementary school from residential area.

FIG. 31 is a diagrammatic representation of a geo-block scoring subsystem that scores and ranks the geo-blocks produced by the geo-block definition subsystem according to certain embodiments.

FIG. 32 is a flowchart illustrating a geo-block scoring method performed by the geo-block scoring subsystem according to certain embodiments.

FIG. 33 is a flowchart illustrating an initializing and/or updating process performed by the geo-fence definition module according to certain embodiments

FIGS. 34A and 34B are map overlay diagrams illustrating exemplary geo-blocks with their associated scores derived based on different campaign parameters or performance goals according to certain embodiment.

FIG. 35 is a map overlay diagram illustrating of an exemplary geo-fence including higher-scoring geo-blocks selected from geo-blocks in a targeted geographical area around a point of interest (POI) according to certain embodiments.

FIG. 36 is a flowchart of a process for geo-block-based targeting according to certain embodiments.

FIGS. 37A-37C are map overlay diagrams of geo-blocks around a point of interest illustrating dynamic inclusion or exclusion of certain geo-blocks based on a pacing status of an information campaign according to certain embodiments.

DESCRIPTION OF THE EMBODIMENTS

As shown in FIG. 1, certain embodiments of the present disclosure provide a system 100 coupled to a packet-based network for detecting lookalike mobile devices communicating with the packet-based network. The system 100 comprises, among other things, a request processor 101, a seed list processor 102, and a lookalike prediction subsystem 103. In certain embodiments, the system 100 is configured to perform one or more methods for lookalike predictions, as described below.

In certain embodiments, the request processor 101 includes or has access to a geo database storing therein data associated with geo-places. In certain embodiments, the geo-places include geo-blocks and geo-fences. Each of the geo-blocks correspond to a geographical region having at least one border defined by a public road or natural boundary. Each of the geo-fences correspond to a plurality of points of interest. The geo database includes a geo-block database storing therein data associated with the geo-blocks and a geo-fence database storing therein data associated with the geo-fences.

In certain embodiments, the request processor 101 is configured to receive requests associated with mobile devices communicating with the packet-based network and to process the requests with respect to the geo places in the geo database to detect location events associated with mobile devices. Each location event corresponds to a time stamp and identifies a geo-place. In certain embodiments, the location events include geo-block-based location events and geo-fence-based location events. Each geo-block-based location event is related to a geo-block in the geo-block database, and each geo-fence-based location event is related to a name or brand of a point of interest (POI) having a geo-fence in the geo-fence databases.

In certain embodiments, the seed list processor 102 includes a client interface configured to receive seed list data files from clients via the packet-based network, and to parse each data file to extract a list of seed mobile devices and lookalike discovery specifications. If available in the data file, this process can also extract a weight associated with each seed mobile device. The weight can be used to reflect difference in value for finding lookalike mobile devices for the different mobile devices on the seed list.

In certain embodiments, the lookalike prediction subsystem 103 includes a feature generator configured to construct a set of features for each of a plurality of mobile devices, a machine learning module configured to train a prediction model corresponding to a seed list of mobile users using the features associated with a subset of the plurality of mobile devices, and a prediction module configured to apply the prediction model to the features associated with at least some of the plurality of mobile devices to predict lookalike probabilities of the at least some of the plurality of mobile devices.

In certain embodiments, the lookalike prediction subsystem 103 is further configured to determine a relevance measure for each of the plurality of geo-blocks with respect to the seed list and the plurality of geo-blocks are divided into a number of geo-block brackets each corresponding to a distinct range of relevance measures. the lookalike prediction subsystem 103 may also determine a relevance measure for each of a plurality of big brands with respect to the seed list and divide the plurality of brands into a number of big brand brackets each corresponding to a distinct range of relevance measures. The lookalike prediction subsystem 103 is further configured to construct the set of features for each of the mobile devices by generating one or more features related to each of the number of geo-block brackets, generating one or more features related to each of one or more special geo-blocks, generating features related to each of the plurality of big brands or big brand bracket, as well as location and/or non-location other features.

Thus, the system 100 functions to consolidate raw request data into meaningful features suitable for machine learning and generate lookalike predictions using machine-learned prediction models.

FIG. 2 is a schematic diagram illustrating an overview of an environment 201 in which some embodiments of the disclosed technology may operate. Environment 201 can include one or more computer systems 220 coupled to a packet-based network 200. The packet-based network 200 in certain embodiments includes the Internet 210 and part or all of a cellular network 211 coupled to the Internet 210 via an Internet Gateway. The computers/servers 220 can be coupled to the Internet 210 using wired Ethernet and optionally Power over Ethernet (PoE), WiFi, and/or cellular connections via the cellular network 211 including a plurality of cellular towers 211 a. The network may also include one or more network attached storage (NAS) systems 221, which are computer data storage servers connected to a computer network to provide data access to a heterogeneous group of clients. As shown in FIG. 2, one or more mobile devices 230 such as smart phones or tablet computers are also coupled to the packet-based network via cellular connections to the cellular network 211. When a WiFi hotspot (such as hotspot 235) is available, a mobile device 230 may connect to the Internet 210 via a WiFi hotspot 235 using its built-in WiFi connection. Thus, the mobile devices 230 may interact with computers/servers 220 coupled to the Internet 210. A mobile device 230, or its user, or anyone or anything associated with it, or any combination thereof, is sometimes referred to herein as a mobile entity.

FIG. 3 illustrates a diagrammatic representation of a computer/server 220 according to certain embodiments. The computer/server 220 may operate as a standalone device or as a peer computing device in a peer-to-peer (or distributed) network computing environment. As shown in FIG. 3, the computer/server 220 includes one or more processors 302 (e.g., a central processing unit (CPU), a graphic processing unit (GPU), and/or a digital signal processor (DSP)) and a system or main memory 304 coupled to each other via a system bus 300. The computer/server 220 may further include static memory 306, a network interface device 308, a storage unit 310, one or more display devices 330, one or more input devices 334, and a signal generation device (e.g., a speaker) 336, with which the processor(s) 302 can communicate via the system bus 300.

In certain embodiments, the display device(s) 330 include one or more graphics display units (e.g., a plasma display panel (PDP), a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)). The input device(s) 334 may include an alphanumeric input device (e.g., a keyboard), a cursor control device (e.g., a mouse, trackball, joystick, motion sensor, or other pointing instrument). The storage unit 310 includes a machine-readable medium 312 on which is stored instructions 316 (e.g., software) that enable anyone or more of the systems, methodologies or functions described herein. The storage unit 310 may also store data 318 used and/or generated by the systems, methodologies or functions. The instructions 316 (e.g., software) may be loaded, completely or partially, within the main memory 304 or within the processor 302 (e.g., within a processor's cache memory) during execution thereof by the computer/server 220. Thus, the main memory 304 and the processor 302 also constitute machine-readable media.

In certain embodiments, the procedures, devices, and processes described herein constitute a computer program product, including a non-transitory computer-readable medium, e.g., a removable storage medium such as one or more DVD-ROM's, CD-ROM's, diskettes, tapes, etc., that provides at least a portion of the software instructions for the system. Such a computer program product can be installed by any suitable software installation procedure, as is well known in the art. In another embodiment, at least a portion of the software instructions may also be downloaded over a cable, communication and/or wireless connection.

The system 100 according to certain embodiments can be implemented using one or more computers/servers 220 executing programs to carry out the functions and methods disclosed herein. It should be understood that the example embodiments described herein may be implemented in many different ways. In some instances, the various methods and machines described herein may each be implemented by one or more physical, virtual or hybrid general purpose computers each having a central processor, memory, disk or other mass storage, communication interface(s), input/output (I/O) device(s), and other peripherals. The general purpose computers are transformed into the machines that execute the methods described herein, for example, by loading software instructions into one or more data processors, and then causing execution of the instructions to carry out the functions described herein. As shown in FIG. 2, some of the computers/servers 220 are coupled to each other via a local area network (LAN) 210, which in turn is coupled to the Internet 210. Also, each computer/server 220 referred herein can include any collection of computing devices.

According to certain embodiments, as shown in FIG. 1, the system 100 includes a front-end server that receives requests from the packet-based network 200. These requests may be generated by one or more computers/servers 220 in the packet-based network as they provide mobile services to the mobile devices. In certain embodiments, the system 100 further includes a location module coupled to the front-end server and configured to detect the location of a mobile device associated with each of the requests. In certain embodiment, the location module is further configured to examine the location data in each received request to determine whether they include a reliable latitude/longitude (LL) pair, and if the request does not include a reliable LL pair, the location module would proceed to derive the location of the associated mobile device from other information in the location data, as described in more detail in commonly owned U.S. Pat. No. 9,886,703, issued on Feb. 6, 2018, which is incorporated herein by reference in its entirety. The system 100 further includes a geo-fencing module coupled to the location module and configured to determine if the detected mobile device location triggers any geo-place(s) in a geo-database and returns the triggered geo-place(s) to the front-end server. In certain embodiments, the geo-places include geo-fences and geo-blocks, and the geo database is a spatial database optimized for storing and querying data that represent geographical areas or spaces and may include spatial data and meta data associated with each of the geographical areas or spaces.

In certain embodiments, the geo-fences in the geo database include spatial data representing virtual perimeters of defined areas or places that mirror real-world geographical areas associated with various entities and/or brands. A defined area according to certain embodiments can be a static circle around a business location, e.g. a fence obtained using offline index databases such as InfoUSA (www.infousa.com), which provides a list of POIs and their locations, or areas specified by marketers using predefined boundaries, such as neighborhood boundaries, school attendance zones, or parcel boundaries, etc.

In certain embodiments, the defined areas include one or more geo-fences for each of a plurality of points of interests in consideration of the map data around the POI. For example, as shown in FIG. 4, one or more polygons are defined for the Costco Almaden store 401 to be in conformity with the real-world geographical structure and boundaries of the store and its surroundings, such as a first polygon 410 around the building of the store, a second polygon 420 around the building and its parking lot, and/or a third polygon 430 around a shopping area or business region including the store and other points of interests (POIs). In certain embodiments, these different types of geo-fences are defined for a point of interest (POI) to indicate different levels of intentions, interests, and/or behavior, etc., of a mobile user with respect to the POI, which can be used for location prediction purposes.

Thus, in certain embodiments, different types of geo-fences are associated with a business and may include, for example, (1) a business center (BC) represented by, for example, a polygon corresponding to the perimeter of the building of the business (e.g., the first polygon 410 in FIG. 4); (2) a business premise (BP) represented by a polygon corresponding to the perimeter of the business building and the neighboring parking lots (e.g., the second polygon 420 in FIG. 4); and (3) a business region (BR) or area represented by a polygon corresponding to the perimeter of a shopping center or business or commercial area in which this business is located (e.g., the third polygon 430 in FIG. 4). If a business center is triggered by a mobile device location, it can be reliably inferred that the user of the mobile device is interested in the business by actually visiting it. Triggering of a business premise provides good indication of an intent to visit the business, but not as strong as triggering the business center. If a user triggers a business region, the intent may be regarded as valid but weaker than that from triggering a business premise.

FIG. 5 illustrates examples of some of the geo-fences in the geo database, according to certain embodiments. As shown, the site Costco in Almaden has three different types of geo-fences associated with it—geo-fence with Fence ID 19-35175 corresponds to a business center (BC), which is defined by a polygon around the store building and represented by spatial index a1, a2, . . . , ai; geo-fence with Fence ID 19-35176 corresponds to a polygon around the site's larger premise including its parking lot and represented by spatial index b1, b2, . . . , bj; and geo-fence with Fence ID 19-35177 corresponds to polygon around the shopping center including the store and other POIs and represented by spatial index c1, c2, . . . , ck. Note that geo-fence with Fence ID 19-35177 is also associated with the names/brands of other POIs in the shopping center, as well as name of the shopping center itself. FIG. 5 also shows that the site T.J. Maxx is associated with Fence ID 19-35177 and also has two other types of fences associated with it, and the site Trader Joe's is also associated with Fence ID 19-35177 and has at least a business center place associated with it. As shown in FIG. 5, each geo-fence entry in the geo database includes the spatial data associated with the respective place together with some meta data about the respective place, such as, for example, one or more names/brands associated with the place, a category of the place, a place identifier identifying a particular locale (e.g., city, district, etc.) for the place, the place type, and/or one or more doc IDs identifying one or more information documents (e.g., one or more html/JavaScript files) associated with the names/brands or the place. In most cases, a POI's name is established as its brand, so they are used interchangeably. For ease of discussion, the brand of a POI is referred to hereafter as either the name or the brand of the POI, whichever is associated with the POI in the geo-fence database.

In certain embodiments, the geo-blocks in the geo database represent geographical regions with natural boundaries such as major roads, shorelines, mountain ranges, etc., as described in further detail below. FIG. 6 illustrates graphically exemplary geo-blocks according to certain embodiments. In this example, for an area in the city of Santa Clara, Calif., the geo-blocks are shown as outlined in boundaries overlaid on top of a map for the area, taken from, for example, Google Map, and the boundaries of the geo-blocks are mostly aligned with major roads and natural boundaries, taking into account the road width so as to exclude mobile signals from travelers on the major roads.

For example, geo-block 601 containing the Moonlite Shopping Center is shown to be bordered on three sides by major roads, El Camino Real, Bowers Ave, and Benton St., respectively, and on another side by the Saratoga Creek. Each of the geo-blocks shown in FIG. 6 can be further partitioned into more granular blocks bordered by smaller roads. Real world entities present in these geo-blocks tend to serve common functional purposes (residential, retail etc.), and these blocks form the foundation for the construction of boundaries that are highly indicative of location dependent attributes such as intention and demographics. FIG. 7 illustrates examples of some of the geo-blocks in the geo database, according to certain embodiments. As shown, each geo-block includes spatial data defining the boundary of the geo-block and meta data including, for example, the city/state in which the geo-block is located, the functionality of the geo-block (e.g., residential, retail, recreational, educational, etc.), one or more major POIs in the geo-block, as well as other information such as demographic of the residents or visitors of the geo-block, and inventory of requests with location data in the geo-block, etc., which can be derived from logged request data.

In certain embodiments, as shown in FIG. 8A, the front-end server receives a request 801 from, for example, a server run by a mobile service provider (MSP or MSP server), via the network 200. The request 801 includes a request ID, mobile device data such as mobile device ID, maker/model, operating system, etc., mobile entity data such as user ID (UID), age, gender, income bracket, education level, etc., mobile device location data including a plurality of location components, such as latitude and longitude coordinates (LL), IP addresses (IP), postal or zip codes (ZC), and/or city-state names (CS), etc. The request may further include other information. In certain embodiments, the front-end server validates the location information by checking the validity and consistency of the location components and by weeding out any invalid location component(s). Generally, the LL is usually believed to be the most useful location component. However, when a mobile entity doesn't allow its location information to be known, mobile applications at the MSP server typically provide only coarse location data in the form of, for example, an IP address, a ZC (e.g. entered by the user at the time of registration), or CS. Thus, mobile applications at the MSP server frequently provide LLs obtained from geo-coding software, which translates ZC, CS, and other points of interests into one representative LL. In one embodiment, such representative LLs are categorized as “bad LLs”. A bad LL can be, for example, a centroid of a ZC/CS, or any fixed point on a map (e.g. (0,0) or an arbitrary location).

In certain embodiments, the location module is configured to weed out the bad LL's, so that location data with bad LL's are not provided to the next stage processing, by using the techniques disclosed in commonly owned U.S. patent application Ser. No. 14/716,816, entitled “System and Method for Estimating Mobile Device Locations,” filed on May 19, 2015, which is incorporated herein by reference in its entirety.

The location module is further configured to estimate the location of the mobile device from the request 801 and generate location data to represent an estimated mobile device location, which may be a geographical point represented by a lat/long pair or one or more probable areas or regions the mobile device is estimated to be in, as shown in processed request 802 with generated location data in FIG. 8B. The geo-fencing module queries the geo database with the lat/long pair or the one or more probable regions to determine whether the location data triggers one or more geo-places in the geo database, and returns the triggered geo-place(s) to the front-end server. In certain embodiments, the front end server annotates the request 801 with the triggered geo-place(s) to generate an annotated request 810, and outputs the annotated request 810 to buffer 1, which buffers and outputs the annotated request 810 to a request log. The triggered geo-place(s) may include a geo-block (if the mobile device is in a place that has been geo-blocked) and may further include one or more geo-fences if the estimated location or probable area or region is in or overlaps with the one or more geo-fences, as shown in FIG. 8C. For ease of description, the triggering of a geo-place (e.g., a geo-block or a geo-fence) is sometimes referred to herein as a location event. So, an annotated request may include one or more location events.

FIG. 9 is a table illustrating exemplary entries in the request log, according to certain embodiments. Each entry in the request log corresponds to a respective processed (or annotated) request and includes at least some of the data in the respective annotated request, such as request (or packet) ID, mobile device information such as mobile device ID, make/model, mobile user information such as UID, age, gender, eduction, etc., a latitude/longitude pair, data related to location events involving triggered geo-fence(s) and/or a geo-block, mobile application used at the time of the request, and the time stamp of the request, etc.

In certain embodiments, as shown in FIG. 8A and FIG. 9, the request 801 received from the Internet by the front-end server includes other information as well as the location information, such as an application program running on the mobile device, a time stamp indicating the time of the request (e.g., day, hour, minute, etc.), one or more keywords suggesting types of information for returning to the mobile device, and/or other information associated with the mobile user, the mobile device, and/or the MSP. In some cases, the location data can trigger multiple places. For example, as shown in FIG. 4, a request that triggers the BC place 410 of Costco Almaden also triggers the BR place 430 of any of the POIs in the same business region as well as the geo-fence for the business region (e.g., a retail center or shopping mall). Thus, the request may be annotated with the BR place of one or more other POIs in the same business region, as well as the BC place of Costco Almaden. For the business region itself, the BR place may be the only geo-fenced place associated therewith, so the business region is triggered as long as the associated BR place is triggered.

Each location invent involving a triggered geo-fence or a triggered geo-block is included in the annotated request together with information about the triggered geo-fence or geo-block. If a request triggers multiple places associated with a brand, only the smallest of the places (e.g., the BC or the BP place) is included as a location event. As shown in FIG. 8C, some or all of the meta data 812 of a triggered geo-fence and some or all of the meta data 814 of the triggered geo-block can be included in the annotated request 810.

The system 100 further includes a document (or information) server configured to receive the annotated request 810 output from the front-end server and to evaluate the annotated request 810 to determine whether to serve a document in response to the request and which document to select for transmission to the MSP server (or another server) via the network 200. In certain embodiments, the information server is a computer server, e.g., a web server, backed by a database server that information sponsors use to periodically update the content thereof and may store information documents. Each of the information documents may be stored in the form of, for example, an html/JavaScript file or a link thereto, which, when loaded on a mobile device, displays information in the form of, for examples, a banner (static images/animation) or text. In certain embodiments, the system 100 further includes an lookalike prediction subsystem 103 configured to generate off-line location predictions, which are stored in a prediction library for querying by the document server, and an on-line prediction subsystem 120 configured to generate on-line (or real-time) location predictions, which are provided to the document server in real-time, as explained in further detail below. In certain embodiments, the document server evaluates the annotated request 810 based on the off-line location predictions and/or the on-line location predictions, as well as other factors, as explained below.

In certain embodiments, the document selected for transmission to the MSP can be provided in the form of, for example, an html/JavaScript file, or a link to a universal resource location (URL), which can be used by the MSP or a mobile device to fetch the html/JavaScript file. The html/JavaScript file, once displayed or impressed on a mobile device, may also include one or more links that an interested user can click to access a webpage or place a call using the mobile device. The webpage enables the user of the mobile device to take secondary actions such as downloading an app or make an on-line purchase.

In certain embodiments, the html/JavaScript file is designed such that when it is displayed or impressed on a mobile device, a signal is sent by the MSP server or the mobile device automatically to the document server either directly or via another server (e.g., the MSP server so that the document server can keep track of whether the file has really been impressed on the mobile device. In certain embodiments, mechanism are also put in place such that when any of the one or more links are clicked, or when the mobile user download an app or make a purchase from a linked webpage, a signal is also sent from the mobile device to the document server in the background either directly or indirectly so that the document server can keep track of the clicks/calls or secondary actions made in response to the impression. The document server provides data of such feedback events (i.e., impressions, clicks/calls, and secondary actions) to buffer 2, which buffers and outputs the data to a feedback log. FIG. 10 is a table illustrating exemplary entries in the feedback log, according to certain embodiments.

Thus, raw location data in requests are converted into brands and geo-blocks in processed requests. The logged data in the requests log and the feedback log collected over the period of time (e.g., six months) form a large collection of mobile device data (e.g., millions and millions of annotated requests and impression/click/call events). The dimensions of these data are usually too large to be used directly for meaningful location prediction. In certain embodiments, the lookalike prediction subsystem 103 is configured to reduce the dimensions of the logged data by extracting features and labels from the location data, to train one or more prediction models using the features and labels, and to apply the prediction models to an appropriate feature space to obtain off-line predictions. As shown in FIG. 1, the lookalike prediction subsystem 103 includes an data manager, a mobile device database, a feature generator, a features/labels database, a training module, a prediction models library, an off-line prediction module, an indexer, and an indexed prediction library.

In certain embodiments, the lookalike prediction subsystem 103 is configured to perform a method 1100 illustrated in FIG. 11 while the front end server continues to receive and process incoming requests. As recited in blocks 1110-1130 in FIG. 11 and further illustrated in FIG. 12, the data manager is configured to define a user space 1200 from the request data in the predefined time period. The user space 1200 may include, for example, mobile devices that meet certain requirements, such as having more than a predetermined number of associated requests with time stamps in a predefined time period (e.g., the last six months) in the request log. The users in the user space 1200 should overlap with the users in the seed list 1210. The data manager is further configured to define a sample space including at least some of the mobile devices in the user space. The mobile devices in the sample space may be selected such that each of the mobile devices in the sample space meets the lookalike discovery specifications associated with the seed list, such as specific age and/or gender groups for the associated mobile users or certain requirements for the mobile devices' locations, which may be specified in the externally provided file(s) containing the seed list. Thus, some of the mobile devices 1201 that do not meet the requirements in the lookalike discovery specifications associated with the seed list are carved out, leaving the rest of the users to form the sample space 1220. Seed mobile devices not in the user space 1200 are also not included in the sample space 1220. The data manager then proceeds to randomly select a small percentage (e.g., 2%-10% depending on the size of the sample space) of the users in the sample space 1220 and a roughly equal percentage of the users in the seed list, and partitions the selected users into a training partition (or training set) 1221 and an evaluation partition (or evaluation set) 1222. For example, 80% of the selected users forms the training partition and 20% of the selected users form the evaluation partition. In certain embodiments, all of the selected users are used as the training partition.

As recited in block 1140 in FIG. 11, the data manager is further configured to extract a set of mobile device data corresponding to location events in the predefined time period from entries in the request log having time stamps in the predefined time period. In certain embodiments, as shown in FIG. 13, the data manager includes a search engine configured to search, for each mobile device of a plurality of mobile devices, processed requests associated with the mobile device and having time stamps in the predefined time period (e.g., the past six months), and a buffer configured to buffer the output from the search engine. The plurality of mobile device may include the mobile devices in the training partition and evaluation partition, as well as some or all of the mobile devices in the rest of the sample space. The data manager further includes a compressor configured to compress the buffered data, such that multiple location events corresponding to consecutive time stamps triggered by the mobile device at the same place within a preset time interval (e.g. 1 hour), are reduced to a single location event. For example, as shown in FIG. 9, mobile device with UID 36***412 triggered the same geo-fence B175 and the same geo-block 396841 at different times that are within one hour of each other. The two events related to the geo-fence or the geo-block are reduced to a single event to indicate a single visit by the mobile devise to the triggered geo-fence or geo-block at one of the time stamps (e.g., the earliest time stamp) with a duration computed using the the difference between the earliest time stamp and a latest time stamp within an hour from the earliest time stamp. Another location event by the mobile device at the same place but with a time stamp beyond the preset time interval from the earliest time stamp would be considered another visit to the place by the mobile device, even though the mobile device may have stayed at the same place during the whole time.

In certain embodiments, the search engine can be configured to only search for location events with certain types of geo-fences depending on the associated brands. For example, for certain brands, only location events with triggered BC places are considered as visits to these brands/names, for certain other brands, location events with triggered BP places are sufficient to be considered as visits to these brands, and for some brands, such as retail centers or shopping malls, location events with triggered BR places are considered as visits to these brands.

The data manager further includes another buffer that stores the compressed location events for the mobile device, and an aggregator configured to aggregate the location events to form a set of mobile device data corresponding to location events in the time period for the mobile device. As shown in FIG. 14, the mobile device data 1410 for the mobile device with the UID 36***412 may include, for example, device and user meta data such as age, gender, education level, and other information such as maker/model, operating system, etc., aggregated location events associated with each geo-block triggered by the mobile device during the time period, aggregated location events associated with each brand triggered by the mobile device during the time period, aggregated feedback events associated with one or more documents impressed on the mobile device during the time period, and aggregated usage data associated with mobile applications used on the mobile device during the time period. In certain embodiment, a brand is triggered when a location event 812 includes the brand. Or, if the brand uses multiple types of fences, as described above, the brand is triggered when a location event 812 includes the brand and the fence type specified for the prediction model to be trained.

In certain embodiments, aggregated location events associated with each triggered geo-block (e.g., GBx) or brand (e.g., Bx) includes, for example, a number of visits to the geo-block or brand during the time period, time of last visit during the time period, average length of stay per visit, etc. In certain embodiments, the number of visits to the geo-block or brand is divided among a plurality of time blocks (shown as TB1, TB2, TB3) during a day, such as morning (6:00 am to 12:00 pm), afternoon (12:00 pm to 6:00 pm) and evening (6:00 pm to 6:00 am). Likewise, usage data associated with each mobile application used on the mobile device during the time period are aggregated likewise. The aggregated feedback events associated with each of one or more documents (e.g., Docx) impressed on the mobile device during the time period may include, for example, a number of impressions of the document made on the mobile device during the time period, a number of click/calls the mobile device made on the impressed document, and a number of secondary actions taken with the mobile device in response to the impressed document. These numbers can also be divided among the different time blocks.

The data manager is configured to perform the above searching, compression, and aggregation processes for each of the plurality of mobile devices and to store the compressed and aggregated data for the plurality of mobile devices in the mobile device database. In certain embodiment, as shown in FIG. 14, to reduce storage space in the mobile device database, the compressed and aggregated data for each mobile device (e.g., mobile device with UID 36***412) and for each time period (e.g., time period) is stored as a text string 1420 in the mobile device database.

FIG. 6 shows just a couple of dozens of geo-blocks. In reality, there may be hundreds of thousands or even millions of geo-blocks in a map. So, if event at each of this large number of geo-blocks is considered independently, the feature set or data size can be too large to be manageable. For example, a naïve approach of taking visitation frequency to each geo-block as a single feature introduces an large number of sparse features, leading to poor machine-learning performance. Further, since most of the blocks are not visited or rarely visited by the seed mobile devices, events related to these blocks are not interesting to the lookalike discovery process and can cause noise and errors. The same can be said with regard to the POIs or brands.

Thus, in certain embodiments, multiple geographical regions (e.g., geo-blocks and geo-fences) are grouped together as a single entity and visitation events to each group are aggregated. For brands, the grouping criteria consists of considerations of POI meta information and spatial distribution, e.g. stores of the same retail brand, restaurants in the same spatial cluster. Geo-blocks do not have sufficient meta information for constructing specific grouping rules. Instead, the grouping can be achieved through analytics of comparisons between seed mobile devices and the mobile devices in the sample space. For example, a score or relevance measure for a region can be calculated for each geo-block by taking the ratio of the number of seed mobile devices in the training partition that are associated with location events related to the region to that of all the mobile devices in the training partition that are associated with location events related to the region. The geographical regions are then ranked using the scores and divided into buckets.

In certain embodiments, as recited in block 1150 in FIG. 11, the lookalike prediction subsystem 103 further includes a feature engineering module configured to engineer a set of features corresponding to a specific seed list for each of the plurality of mobile devices according to a feature engineering process 1500 illustrated in FIG. 15. In certain embodiments, the specifications associated with the seed list may include one or more locations of interests. The one or more locations may correspond to, for example, one or more geo-fences associated with, for example, one or more brands or one or more categories in the geo database. The one or more locations of interests are referred to herein as a location group.

As shown in FIG. 15, the feature engineering module is configured to select a set of geo-blocks and determine a relevance measure for each of the geo-blocks with respect to the seed list, as recited in block 1505 in FIG. 15. In certain embodiments, the relevance of a particular geo-block to the lookalike discovery process can be represented by an associated score or relevance measure. The relevance measure for a geo-block can be determined using any of a variety of relevance or performance metrics, as discussed in further detail below. For example, the relevance of a particular geo-block to the seed list can be determined by the number of location events at the particular geo-block involving any mobile device in the seed list and in the training partition as compared to the total number of location events at the particular geo-block involving any of the mobile users in the entire training partition. As another example, the relevance measure for the geo-block with respect to a seed list can be determined by determine a number of distinct mobile devices among the training partition that have triggered the geo-block using logged request data or extracted mobile device data. The relevance measure can simply be the percentage of the number of distinct mobile devices that are on the seed list.

In certain embodiments, the feature engineering module is further configured to assign the selected geoblocks into a number of geo-block (GB) brackets according to their respective relevance measures, as recited in block 1510 in FIG. 15. In certain embodiments, the selected geo-blocks are divided into a number of geo-block brackets each corresponding to a distinct range of relevance measures. For example, as illustrated in FIG. 16, suppose there are 2000 selected geo-blocks, which can be all of the geo-blocks in one or more targeted geo-graphical regions, and there are 100 geo-block brackets (e.g., GBB1, GBB2, GBB100), the geo-blocks in GBB1 could include 20 geo-blocks with the highest relevance measures, the geo-blocks in GBB2 could include 20 geo-blocks with the next highest relevance measures, and so on. Assigning the geo-blocks into geo-block brackets largely reduces the data dimensions.

In certain embodiments, the feature engineering module is further configured to select a set of brands, which may be, for example a set of relatively big brands (BB) that have sizable visits by mobile users to allow sufficient density of data, as recited in block 1505 in FIG. 15. Depending on how many brands are selected, the feature engineering module may be further configured to assign the selected big brands into a number of big brand (BB) brackets according to their respective measures of relevance, as recited in block 1520 in FIG. 15. The feature engineering module may be configured to determine the relevance measure for each selected brand with respect to the seed list. The relevance measure for a brand can be determined as the relevance measure for a geo-block, as discussed above, using logged request data or extracted mobile device data.

In certain embodiments, similar to assigning geo-blocks to geo-block brackets, as discussed above, the selected brands are divided into a number of big brand brackets (BBB) each corresponding to a distinct range of relevance measures. For example, suppose there are 1000 selected brands, and there are 20 big brand brackets (e.g., BBB1, BBB2, . . . , BBB20), the brands in BBB1 could include 50 brands with the highest relevance measures, the brands in BBB2 could include 50 geo-blocks with the next highest relevance measures, and so on. Selecting the big brands and optionally assigning them to the big brand brackets further reduces the data dimensions.

The feature engineering module is further configured to construct a set of features for each of the plurality of mobile devices using the mobile device data associated with the mobile device and corresponding to the training time period. As shown in FIG. 15, the feature engineering module is configured to: select a user from among a plurality of users (block 1525), generate features related to each geo-block bracket for the user (block 1530), generate features related to special geo-blocks related to the seed list for the user (block 1535), identify a set of most frequently visited geo-blocks (MFVGB-1, . . . , MFVGB-n) for the user and generate features related to each of the MFVGBs for the user (block 1540), generate features related to each BB or BB bracket (BBB) for the user (block 1545), and generate one or more other features for the user (block 1550). In certain embodiments, the set of MFVGBs may include a MFVGB from each of a plurality of geo-block functionalities, such as retail, residential, industrial, etc. Thus, the MFVGBs may include a residential MFVGB, which could be the home of the mobile user, an industrial MFVGB, which could be the workplace of the mobile user, and a retail MFVGB, which may be where the individual does most of the shopping, etc.

FIG. 17 illustrates as examples a set of features for a mobile device with UID 52**256 for the time period. As shown in FIG. 16, the set of features may include device/user meta data. The features related to each GBB of the geo-block brackets (GBB₁, GBB₂, . . . , GBB_(m)) include a number of visits to any geo-block in the GBB during the time period, time of last visit to any geo-block in the GBB during the time period, an average length of stay per visit to any geo-block in the GBB during the time period, etc. In certain embodiments, the number of visits to the GBB is divided among a plurality of time blocks (shown as TB1, TB2, TB3) during a day, such as morning (6:00 am to 12:00 pm), afternoon (12:00 pm to 6:00 pm) and evening (6:00 pm to 6:00 am).

Likewise, the features related to each BB or BBB of the big brands (BB₁, BB₂, . . . , BB_(m)) or big brand brackets (BBB₁, BBB₂, . . . , BBB_(m)) include a number of visits to the BB or any brand in the BBB during the time period, time of last visit to the BB or any brand in the BBB during the time period, an average length of stay per visit to the BB or any brand in the BBB during the time period, etc. In certain embodiments, the number of visits to the BB or any brand in the BBB is divided among a plurality of time blocks (shown as TB1, TB2, TB3) during a day, such as morning (6:00 am to 12:00 pm), afternoon (12:00 pm to 6:00 pm) and evening (6:00 pm to 6:00 am).

The special geo-blocks can include, for example, retail geo-blocks. A retail geo-block is a geo-block having a retail functionality, as indicated by its associated meta data. In certain embodiments, the features related to the retail geo-blocks among the selected geo-blocks include a number of weighted visits and a number of net visits. The number of net visits is the number of visits made with the mobile device to any of the retail blocks within the time period, as determined using the mobile device data associated with the mobile device and corresponding to the the time period. The number of weighted visits is the weighted sum of a number of visits to each of the retail geo-blocks multiplied by a weight of the retail geo-block. The weight of the retail geo-block can be computed based on a fifth number of distinct mobile devices that triggered the retail geo-block during a pre-selected time period and a sixth number of the mobile devices that triggered the retail geo-block and also triggered a brand associated with any of the locations in the seed list during the same time period. The weight can simply be a ratio of the sixth number to the fifth number or some other combination of the two numbers and/or other factors. The sixth number and the fifth number can be determined using logged request data or extracted mobile device data.

In certain embodiments, the most frequently visited geo-block (MFVGB) is the geo-block that has the most number of visits from the mobile device compared to the other selected geo-blocks. The features associated with the MFVGB can include for example, a number of visits to the MFVGB by the mobile device during the time period, and the distance from the MFVGB to a nearest location among the locations in the seed list. In certain embodiments, the number of visits to the MFVGB is divided among a plurality of time blocks (shown as TB1, TB2, TB3) during a day, such as morning (6:00 am to 12:00 pm), afternoon (12:00 pm to 6:00 pm) and evening (6:00 pm to 6:00 am).

In certain embodiments, the set of features for the mobile device may include other features, such as mobility features and feedback features. The mobility features may include, for example, a number of distinct brands triggered by the mobile device during the time period, and a GB ratio of a number of distinct geo-blocks triggered by the mobile device to the sum of visits to all of the triggered geo-blocks during the time period. The feedback features may include, for example, pre-exposure feature, which may be a number impressions of one or more documents related to the seed list on the mobile device during the time period, a click/call ratio, which may be the ratio of a number of times a click is made on the mobile device in response to the one or more documents to the number of impressions of the one or more documents, and a secondary action ratio, which may be the ratio of a number of times secondary actions are made on the mobile device in response to the one or more documents to the number of impressions of the one or more documents.

In certain embodiments, as recited in block 1160 in FIG. 11, the feature generator is further configured to determine a set of labels corresponding to the seed list, for the training partitions 1221 and the evaluation partitions 1222. In certain embodiments, the set of labels include one label for each of the mobile devices in the training partition and the label is a “1” or “0” depending on whether the mobile device is in the seed list, if the seed list file does not specify different weights for the seed mobile devices. If weights are specified, the label of a mobile device included in the seed list would be its weight (e.g., 0.95, 0.78, etc.), and the label of a mobile device not included in the seed list is “0.” The feature generator may extract a plurality of sets of labels for a plurality of seed lists, respectively, as shown in FIG. 18. Each set of labels is used to train a corresponding prediction model, as explained in further detail below.

As shown in FIG. 1, the lookalike prediction subsystem 103 further includes a training module configured to employ machine learning approaches to train a prediction model using the training features (i.e., features associated with mobile devices in the training partitions) and a set of labels, as recited in block 1170 in FIG. 11. In certain embodiments, the feature sets and associated target values (labels) for the training partition are input to a machine learning process to train a lookalike prediction model. For binary target values, classification models are used, while regression models can be used for treating continuous target values. Any of several conventional Machine Learning models can be used in this process, and the choice is often made based on grounds of performance, flexibility and scalability. For models involving hyper parameters, Cross Validation may be used. The feature engineering or transformation based on location history data, as discussed above, is essential for a model to make effective use of location related information. In certain embodiments, Random Forest [Breiman, Leo (2001). “Random Forests”. Machine Learning. 45 (1): 5-32. doi:10.1023/A:1010933404324] can be used for both regression and classification tasks. Random Forest accepts both categorical and continuous input features, is more robust against overfitting and its hyper-parameters are relatively simple to tune. Moreover, Random Forest can capture complicated structures in data and hence tend to offer good performance over a wide range of practical problems without extensive feature engineering. In some cases, Random Forest can be replaced with Gradient Boosted Trees [Hastie, T.; Tibshirani, R.; Friedman, J. H. (2009). “10. Boosting and Additive Trees”. The Elements of Statistical Learning (2nd ed.). New York: Springer. pp. 337-384. ISBN 0-387-84857-6] to achieve higher performance while enjoying comparable scalability and flexibility in terms of input feature data types. If resource for data storage and computation is limited, light weight models such as Logistic Regression [Hilbe, Joseph M. (2009). Logistic Regression Models. Chapman & Hall/CRC Press. ISBN 978-1-4200-7575-5] can also be used.

The training module may train a prediction model for each of a plurality of seed list and store the prediction models in the prediction model database, as shown in FIG. 1.

In certain embodiments, block 1170 may further includes an evaluation process, in which the prediction model is evaluated by a prediction module in the lookalike prediction subsystem 103, which is configured to apply the prediction model to the feature sets of mobile devices in the evaluation partition 1222 (shown in FIG. 12) and to generate a prediction accuracy measure or similarity metric based on comparison of the lookalike predictions for these mobile devices with the labels determined for these mobile devices in block 1160, as shown in FIG. 19. The accuracy measure or similarity metric may be, for example, the standard deviation between the prediction results and the labels. Thus, a good prediction model should have an accuracy measure that is close to 0. In certain embodiments, a threshold accuracy (e.g., 15%) is imposed so that a prediction model having an accuracy measure above 15% is discarded. If available for the model, this process can also evaluate each feature's contribution to the prediction results.

In certain embodiments, as recited in block 1180 in FIG. 11 and shown in FIG. 1, the prediction module is further configured to apply the prediction model obtained in block 1170 to mobile devices in the sample space 1220 to generate prediction results. In certain embodiments, as shown by the examples in FIG. 20, the prediction results include a list of some or all of the mobile devices in the sample space, together with their calibrated scores or probabilities of being lookalike mobile devices, so as to offer the client full freedom in deciding on trade-offs between scale and external performance evaluation processes. In latter case, it is still desirable for the model to output a continuous score to indicate closeness to the positive target value. The prediction results are indexed and stored in the predictions database (as shown in FIG. 1), and can be used by the doc server in the request processor 101 when determining whether to send certain documents to a mobile user. The prediction results can also be used to rank the mobile devices in the sample space, as shown in FIG. 21, and the top ranked the mobile devices (e.g., with predicted lookalike probabilities higher than 85%) are selected as lookalike mobile devices and included in one or more data files together with their respective prediction results. The one or more files can be constructed and transmitted to the client through the packet-based network by the client interface in the seed list processor 102, as shown in FIG. 1.

Thus, the present disclosure provides methods and systems that utilize mobile device location history and machine learning and generate predicative classification/regression model for lookalike prediction. Location related features, together with other user level information, are extracted, transformed and used as model feature input, and a client specified list of mobile devices or their associated users are used as prediction target. This system makes efficient use of different types of location history and thus offers improved scale and performance. It also enjoys many benefits offered by a machine learning platform, such as automatic adaptation to different lists of seed lists, addition of new features and changes in data statistical properties. This system can also offer location related insight to the seed list through studies on model feature importance.

In certain embodiments, the spatial index and meta data for each of at least some of the geo-blocks in the geo-block database, are generated by a geo-block definition subsystem 2210, as discussed in further detail below. A geo-block scoring subsystem 2220 can be employed to score and rank the geo-blocks produced by the geo-block definition subsystem 2210, according to certain embodiments, as discussed in further detail below. The ranks of the geo-block can then be used to organize the geo-blocks into brackets, as discussed above.

In certain embodiments, the location data in the request associated with the mobile device is also examined with respect to one or more targeting areas in determining whether to deliver certain information to the mobile device. In certain embodiments, the targeting areas are formed using one or more geo-blocks selected based on their relevance measures for a particular information campaign. FIG. 22 is a diagrammatic representation of a information server system 2200 provided by one or more computer/server systems 220, which can serve as the location processor 101 in system 100, according to certain embodiments. System 2200 employs dynamically adjusted targeting areas that utilize location visitation patterns to optimize performance metric driven by campaign goals while ensuring that a total volume of users can be reached for mobile advertising. As shown in FIG. 2 and FIG. 22, the processor(s) 202 in the computer/server system(s) 120, when executing one or more software programs loaded in the respective main memory (or memories) 204, provide the information server system 2200 including a geographical region definition subsystem 2210, a visitation behavior modeling subsystem 2215, a geographical region performance scoring subsystem 2220, a geographical region selection subsystem 2225, a real-time performance metric reporting subsystem 2230, and a location history data-logging subsystem 2235. The system 2200 makes use of a plurality databases storing data used and/or generated by the information server system 2200, including a database 2250 for storing the geometry and meta information of generated geographical regions (or geo-blocks), a database 2255 for storing spatial indices and meta data of geo-places, a database 2260 for storing campaign information, a database 2265 for storing logged mobile supply data, and one or more other databases (e.g., database 2270 for storing computed meta data such as mobile device user behavior model data and database 2275 for storing geographical regions' performance score data, etc.). Any or all of these databases can be located in the storage(s) 210 of the one or more computer systems 120, or in one or more other server/computer system(s) 120 and/or NAS 121 in the network 200, which the process(s) 202 can access via the network interface device 208.

FIG. 23 is a flowchart illustrating a method 2300 performed by the information server system 2200 according to certain embodiments. As shown in FIG. 23, the method 2300 includes a process 2311 performed by the geographical region definition subsystem 2210, in which geographical regions are defined and associated meta information is obtained, as discussed in further detail below. In certain embodiments, various meta information can be mapped to a defined geographical region, such as its functionality (residential, work, retail, etc.), its average mobile user volume and its KPI performance index. The meta information can be made available to the other subsystems in the system 2200 and can be incorporated into the construction of the targeting areas.

The method 2300 further includes visitation behavior modeling process 2316, which models the visitation behavior of intended mobile device users, for example, customers of a particular brand or a particular business entity. In certain embodiment, the visitation behavior modeling subsystem estimates the probability for customers of a particular business entity to visit different geographical regions by first obtaining a sample set of customers of the business entity, then extracting from data provided by subsystem 2235 the visitation history of these sample customers to the geographical regions stored in database 2270.

The method 2300 further includes a performance scoring process 2321, in which a quality or performance score or measure is assigned for each of the geographical regions. In certain embodiment, the score is dependent on specific campaign performance goal(s). For example, in some cases, an ad campaign's goal is to drive more people to visit their branded stores. Then, the performance score of a geographical region can be defined as the likelihood of a user to visit a branded store after the user has visited this particular geographical region. In cases that brand sales revenue is of interest, the performance score can be derived from brand customer visitation behavior and purchase behavior.

In certain embodiments, processes 2311, 2316, and 2321 are performed offline. The method 2300 further includes a real-time or on-line adjustment process 2326 performed by the geographical region selection subsystem 2225. In certain embodiments, the real-time adjustment process 2326 includes several sub-processes, part or all of which can be performed on-line or in real time. As shown in FIG. 23, the real-time adjustment process 2326 includes a geographical region selection process 2382, a geo-fence-based targeting process 2386 and a real-time pacing estimation process 2388. At the start of a campaign, the geographical region scoring subsystem 2220 provides initial targeting areas by selecting certain number of top scoring geographical regions. This number can be determined based on consideration of estimated average performance or average total reachable user volume. These regions are processed to produce a spatial index file, which is then used to detect users whose real time locations fall within an active geo-fence. These users become potential candidates for receiving information service. Concurrently, subsystem 2225 tracks the rate at which information related to the campaign is being served to users (i.e., pacing status) and adjusts the geo-fence accordingly in process 2326. Thus, a balance between performance and pacing can be reached using the method 2300.

FIG. 24 is a diagrammatic representation of the geo-block definition subsystem 2210 provided by one or more computer/server systems 220 according to certain embodiments. As shown in FIG. 24, the processor(s) 202 in the computer/server system(s) 120, when executing a geo-block definition software program 2401 loaded in the main memory 204, provides the geo-block definition subsystem 2210, which includes a geo data extraction module 2410, a geo-block construction module 2420, a real-time data-logging module 2430, a meta data computation module 2440, and a geo-block refining module 2450. The geo-block definition subsystem 2210 makes use of a plurality databases storing data used and/or generated by the geo-block definition subsystem 2210, including a database 2460 for storing the geo-blocks generated by the geo-block construction module 2420 and/or the geo-block refining module 2450, a database 2470 for storing logged mobile supply data, and one or more databases (e.g., database 2480 and 2490) for storing computed meta data such as demographic data and inventory data. Any or all of these databases can be located in the storage 210, or in another server/computer 120 and/or NAS 121 in the network 200, which the process 202 can access via the network interface device 208.

Examples of the geo-blocks created by the subsystem 2210 are illustrated in FIG. 7, according to certain embodiments. In general, the definition of geographical regions is not limited to that described above. A different set of geographical regions with or without its own meta information can also be used for the subsequent processes.

FIG. 25 illustrates a method 2500 performed by the geo-block definition system 2200 according to certain embodiments. As shown in FIG. 25, the geo data extraction module 2410 obtains publicly available transportation route and natural boundary data from a server in the network 200 that provides the data, and extracts and pre-processes (2510) geographical information of transportation routes and natural boundaries (geo-data) based on the transportation route and natural boundary data. The geo block construction module 2420 creates (2520) geo-blocks using the extracted geo data and publicly available map data. The real-time data-logging module 2430 processes and logs (2530) real-time mobile supplies (e.g., requests for advertisement from mobile publishers) with respect to the created geo-blocks. The meta data computation module 2440 obtains (2540) meta data such as location specific attributes from the logged mobile supply data and various data sources. The geo-block refining module 2450 refines (2550) the geo-blocks to improve boundary cases and to incorporate geographical information of real world objects not considered by the geo-block construction module 2420, and to enrich the geo-blocks with relevant meta data.

In process 2510, geographical information of transportation routes (highways, railways, waterways etc.), as well as natural boundaries (coastlines, lake boundaries etc.) are collected. One example data source for this purpose is OpenStreetMap (www.openstreetmap.org/). Geometrically, these objects are described as collections of line segments, together with meta data information such as their type, width and traffic speed. In certain embodiments, these line segments are collected and scored based on their significance, e.g., residential area roads in residential area score lower than highways do. Line segments scored above a threshold are collected to form a line set, which is used in process 2520 to define initial geo-blocks.

In process 2520, the line set defined in process 2510 is used to form polygons with boundaries aligned with the lines in the line set. FIG. 26 illustrates a method 2600 for forming such polygons according to certain embodiments. As shown in FIG. 26, the method 2600 comprises:

(2610) defining a line set

(2620) creating an image of uniform initial color (C1), the size of the image being mapped to geographical area based on some predefined scaling ratio;

(2630) plotting the lines in the line set on the image with a different color (C2), taking into account road widths by plotting the lines with different thicknesses based on their width and scale information;

(2640) searching in the image for pixels in the initial color (C1) as uncovered regions;

(2650) for each uncovered region, identifying the pixels belong to this region using a region-growing algorithm;

(2660) detecting and converting the contours of this region into a polygon representation;

(2670) changing all of the pixels belonging to this region to the color (C2) to indicate that the region is covered;

(2680) determining whether there are still more pixels in color (C1) and repeating processes (2640) through (2670) until no more pixel in color C1 is found; and

(2690) storing the polygon representation as initial geo-blocks.

The polygons thus formed are initial geo-blocks. In certain embodiments, to define geo-blocks on a national or global scale while maintaining sub-meter accuracy, the image processing method 2600 is used on each of multiple small areas and the polygons from the multiple small areas are merged to form initial geo-blocks for a larger area. By using different thresholds, geo-blocks of different granularities can be constructed to form hierarchical layers of geo-blocks. The geo-blocks formed in process 2520 are indexed and stored in the geo-block database 2460.

In certain embodiments, real-time inputs (e.g., ad requests) are processed and logged with respect to the initial geo-blocks in process 2530, as illustrated in FIG. 27. For example, given an incoming ad request or any other signal carrying location information of a mobile device, the location information is processed by a location module, such as the one disclosed in co-pending U.S. patent application Ser. No. 14/716,811, filed May 19, 2015, entitled “System and Method for Marketing Mobile Advertising Supplies,” which is incorporated herein by reference in its entirety. The location module outputs verified or derived mobile device location in the form of, for example, latitude/longitude (lat/long), which is then processed by a block Lookup module. The block lookup module carries out a spatial search against the block index in the geo-block database 2460 to determine which geo-block the mobile device is located in, and returns a block_id identifying the geo-block in which the mobile device is located.

Similarly, the mobile device location is processed by a point of interest (POI) lookup module to determine if the location is associated with any POI (indicating that the user might be visiting the POI). In some implementation, this lookup is implemented as a spatial index search over a POI list, a device is associated with a POI whenever its location triggers an existing POI geo-fence (e.g., a circular fence surrounding a business location of a brand). In some other implementation, a POI is represented as a polygon geo-fence corresponding to the building, area, or the parking lot of the POI. A POI association is identified whenever the device location triggers the POI geo-fence, as described in co-pending U.S. patent application Ser. No. 14/716,811 cited above.

As illustrated in FIG. 27, process 2530 creates five log files for each real-time input triggering a POI: the POI visitation log (SV log), a request log, an impression log (imps log), a click log and a secondary action log (SAR log). The essential components of each log are described as follows:

SV Log: (UID, BRAND_ID, TIMESTAMP, BLOCK_ID)

Request Log: (UID, REQUEST_ID, BLOCK_ID, other typical request meta data)

Imps Log: (UID, REQUEST_ID, BLOCK_ID, other typical imps meta data)

Click Log: (UID, REQUEST_ID, BLOCK_ID, other typical click meta data)

SAR Log: (UID, REQUEST_ID, BLOCK_ID, other typical SAR meta data)

Here UID is the unique device id in the forms of UUID, IDFA, GIDFA or ANDROID_ID; REQUEST_ID is the unique id identifying a particular real-time input (e.g., ad request), BLOCK_ID represents a unique geo-block in which the mobile device associated with the real-time input is located. As an example, FIG. 28 is a table illustrating a request log according to certain embodiments.

In certain embodiments, one or more of the above logs can be used in process 2540 to compute meta data for the geo-blocks, which can be used to determine neighborhood attributes associated with the geo blocks. For example, human activity levels can be studied by counting ad request frequency, and geo-block associations can be determined by finding subsets of geo-blocks that share the presence of the same mobile devices. Furthermore, residential geo-blocks with home zip code data (Infousa is one of such data provider) and map demographical data can be identified. Retail, school or office geo-blocks can be recognized with POI data (Infousa, Tomtom, OpenStreetMap are examples of data providers).

In process 2550, the geo-blocks are refined and enriched by applying merge and/or split of existing geo-blocks and by adding meta data to the geo-blocks. In one embodiment, meta data such as zip data, POI data, and demographic data, and logged real-time input data are overlaid to the existing geo-blocks and each block is evaluated by a merge step and a split step. In the merge step, the block geometry and meta data are used to determine the level of similarity between blocks. For example, two adjacent blocks may be merged if they both are residential areas and showing similar mobile device user behaviors. Another example is that a group of nearby geo-blocks that each have insufficient ad request data may be merged together for statistically more reliable analysis.

In the split step, the meta data is used to determine the neighborhood attributes represented by certain geo-blocks to determine whether and how each of these geo-blocks should be split into multiple smaller geo-blocks each with a more distinct neighborhood attribute. In certain embodiments, further refinement can be made with information of real world objects other than the boundary information used to create the initial geo-blocks. If any inconsistency is identified within a block, a split is carried out to divide a block into a number of smaller blocks each capturing more consistent neighborhoods.

FIG. 29 illustrates the separation of residential areas 2901 (enclosed by blue polygons) and a forest area 2902 by investigating the spatial distribution of 9-digit zip codes (Infousa) or by analyzing logged real-time inputs (e.g., ad requests) with detected locations 2903 represented by the red stars. FIG. 30 demonstrates the separation of an elementary school 3001 from a residential area 3002, where the school boundary data is derived from OpenStreetMap.

In certain embodiments meta data information can be added in process 2550 to the geo-blocks by making use of the meta data computed in process 2540. In one embodiment, a geo block can be tagged by their main functionalities as residential, retail, office, commercial block, and industrial, etc. In some other embodiment, a geo-block can be alternatively or additionally tagged by its major POIs, such as school, hospital, airport, stadium, etc. Exemplary data structures of meta data enriched geo-blocks according to certain embodiments are illustrated in FIG. 8. The added meta data can be used in location-based information services, such as ad targeting, ad performance optimization, location-based social networking, etc.

Thus, the present disclosure provides a system and method that produces geo-blocks by partitioning urban areas using geographical information of transportation routes, natural boundaries and other real world objects that are highly relevant to specific types of human activities. Each geo-block has at least one border defined by a real-world object such as a transportation route, a lake, a river, a hill or mountain range, a recreational area, a boundary of a large developed area, such as a school, an airport, etc., and can possess meta data indicating certain attributes such as neighborhood, office, school, airport etc. Actually, most of the geo-blocks are each bordered on all sides or multiple sides by such real world objects. The geo-blocks thus generate features with high level of relevance to real world location partitions, naturally avoid passing by road traffic, and offer flexible level of granularity for location-based information services and location targeting purposes.

For example, FIG. 31 is a diagrammatic representation of a geo-block scoring subsystem 2220 that scores and ranks the geo-blocks produced by the geo-block definition subsystem 2210 according to certain embodiments. In certain embodiments, the system 2220 is provided by a computer/server system 220, which can be the same computer/server system 220 that also provides the subsystem 2210 or a different computer/server system. As shown in FIG. 31, the processor 202 in a computer/server system 220, when executing a geo-block scoring software program 3101 loaded in the main memory 204, provides the geo-block scoring subsystem 2220, including a geo-block identification module 3110, an inventory estimation module 3120, a key performance index (KPI) estimation module 3130, and a store visitation estimation module 3140. Subsystem 2220 may further include a geo-block selection module 3150. Subsystem 2220 makes use of a plurality of databases storing data used and/or generated by the subsystem 2220, including a database 3160 for storing the geo-blocks generated by the subsystem 2210, a database 3170 for storing logged mobile supply data, one or more databases (e.g., database 3180) for storing block level estimation results, including block-level inventory estimation results, KPI estimation results, and store visitation estimation results, and database 3190 for geo-block selections. Any or all of these databases can be located in the storage 210, or in another server/computer 120 and/or NAS 121 in the network 200, which the process 202 can access via the network interface device 208.

FIG. 32 is a flowchart illustrating a geo-block scoring method 3200 performed by the geo-block scoring subsystem 2220 according to certain embodiments. As shown in FIG. 32, the geo-block scoring method 3200 includes identifying 3210 geo-blocks in a targeted region associated with a point of interest (POI), such as a store associated with a brand or a business entity. As shown in FIG. 35, the targeted region can be a circle 3500 drawn around the POI 1501, or an area of arbitrary shape or scale set up by an advertisement campaign for the brand or business. In certain embodiments, the geo-block identification module 3110 identifies the geo-blocks by searching in the geo-block database 3160 for geo-blocks that substantially overlap with the targeted region 3500 associated with the POI 3501 (e.g., at least 50% of the area of each identified geo-block is inside the targeted region associated with the POI).

The method 3200 further includes estimating block-level inventory (3220), in which the inventory estimation module 3120 estimates inventory in each identified geo-block by aggregating request logs along different time frames and along different meta data dimensions. For example, to estimate daily inventory for male users in the 30-40 age group for block_id 1234568, a straight forward method can be to take a daily average of the total number of requests and the total number of unique UIDs seen in the request log that qualifies the meta data requirements and the block_id requirement in the past one week (or month, etc). In some other embodiment, a linear regression model or time series model is used to predict future inventory based on historical log aggregation data applied on different time frames.

The method 3200 further includes estimating block-level campaign KPI (3230), in which KPI estimation module 3130 makes use of the impression (imp) log, click log and SAR log to estimate key performance indices such as click-through rate (CTR), secondary action rate (SAR), etc. for each identified geo-block. The estimation is represented as (BLOCK_ID, CMP_ID, CTR, TF), and (BLOCK_ID, CMP_ID, SAR, TF), where CMP_ID is the campaign_id and TF is the timeframe used to calculate the KPI. In some implementation, because the size of a geo-block is relatively small, and a typical campaign runs only for one or two months, it is difficult to collect enough impression and click data at the block level to reliably calculate KPI. For example, it may sometimes require at least 2000 to 5000 impressions to reliably estimate CTR given that the average CTR stands at about 0.5%, and at least 100 or 200 clicks in order to reliably estimate SAR, with average SAR stands at 5%-7%.

To address this issue, in some embodiment, the KPI estimation is rolled up from campaign to vertical level, and the estimation of CTR and SAR are therefore represented as tuples of (BLOCK_ID, VERTICAL ID, CTR, TF), and (BLOCK_ID, VERTICAL ID, SAR, TF). Since vertical is not limited by the life cycle of individual campaigns, the time frame of aggregation could also be extended to up to 6 months to get better numbers for KPI estimation.

In some implementation, the rollup in the time frame dimension is also needed to support better KPI estimation. For a particular block, the KPI can be first estimated using data in the past 3 months. If insufficient amount of data is collected, data in the past 6 months is used. In some embodiments, the time frame could be rolled up to 1 year or beyond. In some embodiments, the rollup in the time frame dimension could be weighted such that more recent data points get higher weight than older data points. If rolling up in the time frame dimension cannot produce enough data to calculate KPI for some geo-blocks, averaging across the global campaign level or the global vertical level can be used to estimate KPI for these geo-blocks.

The method 3200 further includes estimating block-level store visitation (SV) (3240) score, in which the store visitation estimation module 3140 calculates a brand visitation likelihood score (SV score) for each identified geo-block. In cases that brand sales revenue is of interest, this likelihood score can be derived from brand customer visitation behavior and purchase behavior. In one embodiment, this likelihood score is measured by store visitation rate (SVR), which is defined as the percentage of unique UIDs seen in a geo-block (BLOCK_ID) that have visited a brand (BRAND_ID) during a given timeframe (TF). This is calculated by using the SV log in the user behavior model database 2270 and Request log in the location history database 2265 as follows:

(a) find all the UIDs from the Request log whose location is covered by the given block (BLOCK_ID) at least once during the timeframe (TF), count the total unique number of UIDs, which defines the block_unique variable;

(b) find the UIDs from the (a) set who have made at least one (or n, where n>0) store visitation (SV) to the interested brand (BRAND_ID) from the SV log during the timeframe TF, and count the total unique number of UIDs, which defines the block_sv variable;

(c) compute the SVR using the two unique UIDs variables:

block_svr=block_sv/block_unique

Alternatively, block_sv instead of block_svr is used directly as the SV score on the assumption that the average block size is similar and a higher block_sv directly indicates higher SV likelihood.

In certain embodiments, the SV score is computed as in step (b), but considering only users who visited a brand with some repeated pattern. For example, SV score could be defined as the number of users who visited a brand at least once per week in the given time frame TF.

The method 3200 further includes initializing and/or updating a selection of geo-blocks for each campaign (3250), in which the geo-block selection module 3150 determines an optimized set of initial geo-blocks 3190 for a particular campaign based on the inventory estimation, KPI estimation and store visitation estimation feeds from modules 3120, 3130, and 3140.

FIG. 33 is a flowchart illustrating an initializing and/or updating process 3250 performed by the geo-block selection module 3150 according to certain embodiments. As shown in FIG. 33, the process 3250 includes determining a performance score measure based on the goal of a campaign (3252). For example, if the goal of a campaign is to maximize user clicking engagement, CTR is used as the performance score. Or, if the focus of the campaign is post-click secondary action, then the product of CTR and SAR, which is typically referred to as yield

YIELD=CTR*SAR,

could be used as the score. Or, if the campaign goal is to reach brand loyalists, SVR (block_svr) and/or SV (block_sv) could be used. In a more general case, the score measure could be represented as a weighted sum of these different parameters:

Score=w1*CTR+w2*YIELD+w3*SVR+w4*SV

where w1, w2, w3, w4 are tune-able weight factors based on the specific campaign goal. CTR and SAR*CTR are two possible KPI goals for a campaign; and SVR and SV are two possible SV score estimations as described.

In certain embodiments, the block quality score is defined using normalized variables as

Score=w1*N(CTR)+w2*N(YIELD)+w3*N(SVR)+w4*N(SV)

where the normalization function NO can be a Gaussian normalization function, such as

N(x)=(x−m)/STD

with m being the average of x and STD being the standard deviation of the x variable for the targetable geo-blocks (i.e., geo-blocks in the targeted region for the given campaign). In certain embodiments, process 3250 further includes computing geo-block performance score for each identified geo-block in the targeted region for the campaign based on the campaign performance score measure (3254). Note that the targeted region is a variable set by the campaign. The region could be a circular radius around the brand's business location, a number of zip codes, a city, a state or even a nation.

In certain embodiment, the performance score for a geographical region (or geo-block) is dependent on the specific campaign performance goal(s). For example, in some cases, an ad campaign's goal is to drive more people to visit their branded stores. Then the performance score of a geographical region can be defined as the likelihood of a user to visit a branded store after the user has visited this geographical region. In certain embodiment the following procedure can be used to estimate the likelihood and derive a performance score for each geographical region:

-   -   (a) estimate the probability or rate, Pa, for brand customers to         visit a geographical region, as discussed above and in         co-pending U.S. patent application Ser. No. 15/289,104, filed         Oct. 7, 2016, entitled “Method and Apparatus for Measuring         Effect of Information Delivered to Mobile Devices,” which is         incorporated herein by reference in its entirety;     -   (b) estimate the probability, Pb, for the general public in a         local area (e.g., within 20 miles of a POI) to visit a         geographical region; and     -   (c) use the ratio Pa/Pb for each geographical region as an         estimation of the likelihood for a person visiting a         geographical region to also visit the brand of interest. This         estimation can be used by itself or combined with other factors         such as KPI scores, for example, using, for example, weighted         averages, to obtain the performance score for a geo-block.

Thus, the geo-blocks can be scored differently for information campaigns with different interests or parameters. For example, FIG. 34A illustrate scores of geo-blocks around a POI 3401 represented by the small square 3401 near the center of the plot for an information campaign, where the darker colored geo-blocks represent geo-blocks with higher performance scores. FIG. 34B illustrate scores of the same geo-blocks around the POI 3401 for a different information campaign, where the darker colored geo-blocks represent geo-blocks with higher performance scores. As shown in these figures, the relative scores of the same geo-blocks around a same POI can be very different for different campaign parameters or goals. For example, geo-block(s) 3402 has a relatively higher score than geo-block 3403 in FIG. 34A but a relatively lower score than geo-block 3403 in FIG. 34B.

In certain embodiments, process 3250 further includes ranking the identified geo-blocks in the targeted region based on their performance scores (3256), and selecting the geo-blocks with the best performance scores to form the targeting areas for the campaign (3258). In certain embodiments, geo-blocks with performance scores above a certain threshold are selected. In certain embodiments, block level inventory estimation can be used to guide the selection process to make sure that enough blocks are included in the targeting areas such that the total inventory is sufficient for the campaign budget purpose. For example, if a Walmart campaign has a daily budget of $5000, then the selected geo-blocks should have a total daily inventory of at least $5000. In many cases, the daily inventory provision should be well above the budget in order to guarantee smooth delivery.

FIG. 35 illustrates an example of geo-blocks selected to form targeting areas for a hyperlocal campaign for a Walmart store in Mountain View, Calif. (POI). The circle 3500 is the targeted region of the campaign, the geo-block 3502 shown in pink near the center of the circle is the block containing the POI 3501 (i.e., the Walmart store), and the geo-blocks in dark gray (i.e., geo-blocks 3503, 3504, 3506, and 3507) are the top performing geo-blocks selected for campaign delivery. The gray geo-blocks 3503, 3504, 3506, and 3507 are selected from among geo-blocks that substantially overlap (e.g., by more than half of their respective area) with the targeted region 3500, and together define a dynamic geo-fence or targeting areas for the POI. Note that geo-block 3503 is selected over other geo-blocks (e.g., geo-blocks 3507, 3508, and 3509) that are actually closer to the POI 3501 than the geo-block 3503 and is thus separated from the POI and one or more other selected geo-blocks by one or more non-selected geo-block. In this example, except geo-block 3505, the other selected geo-blocks are not adjacent to the geo-block 3502 containing the POI. Also, the selected geo-blocks may not even include the geo-block 3502 containing the POI, as illustrated in this example. Thus, the targeting areas formed using the methods in the present disclosure are more attune to optimizing the performance of specific campaigns by selecting targeted regions based on likelihood of success, rather than just proximity to the POI.

In some further implementation, the KPI scores and the SVR and SV scores may be estimated at different times of the day, which means the quality score of each block also evolves by time. This leads to a time-varying dynamic fence design, which may define different fences for the morning hours and for the evening hours.

Referring to FIG. 36, according to certain embodiments, the geographical region selection subsystem 2225 includes a geo-block-based targeting module 3610, a real-time pacing estimation module 3630, a geographical region selection module 3640 and a spatial index building module 3650, which are provided by one or more computer/server systems 220 executing one or more software programs. The geo-block-based targeting module 3610 receives and processes information requests presented by an information server, e.g., mobile publishers, ad middleman, and/or ad exchanges, etc. via the network 210. Each information request is related to a mobile device and arrives at the geo-block-based targeting module 3610 in the form of, for example, a data packet including data unites carrying respective information, such as identification of the mobile device (or its user) (UID), maker/model of the mobile device (e.g., iPhone 6S), an operating system running on the mobile device (e.g., iOS 10.0.1), attributes of a user of the mobile device (e.g., age, gender, education, income level, etc.), location of the mobile device (e.g., city, state, zip code, IP address, latitude/longitude or LL, etc.). The request data packet may also include a request time stamp, a request ID, and other data/information.

The geo-block-based targeting module 3610 in certain embodiments performs a method 3600 for processing the request data packet, as illustrated in FIG. 36. The method 3600 comprises receiving an information request via connections to a network such as the Internet (3611), deriving a mobile device location based on the location data in the information request (3613), determining if the mobile device location triggers one or more predefined places or geo-fences (3615), taking steps to fulfill the request if the mobile device location triggers one or more predefined places or geo-fences (3617), and storing information in the processed request in the location history database 2265 for analysis (3619).

In certain embodiments, deriving the mobile device location (3613) comprises processing the location information in the requests using the smart location system and method described in co-pending U.S. patent application Ser. No. 14/716,816, filed May 19, 2015, entitled “System and Method for Estimating Mobile Device Locations,” which is incorporated herein by reference in its entirety. The derived mobile device location is used to search in the spatial index database 2255 for a geo-fence in which the mobile device related to the request may be located. If the ad request is found to have triggered a geo-fence in the spatial index database 2255, the request is annotated with tags corresponding to the geo-fence. The tags may identify business/brand names, categories of the products or services associated with the business/brand names, and the geo-fence, etc., resulting in an annotated request. The processed requests are stored in a request log in the database 2265.

In certain embodiments, fulfilling the request may include comparing the annotated request with matching criteria of a number of information campaigns stored in the campaign database 2260, taking into consideration other factors such as budget, pacing, etc. In certain embodiment, fulfilling the request may include providing the annotated request to an information server system, which uses real-time bidding (RTB). In typical ad serving systems based on Real Time Bidding (RTB), a qualifying request does not always get fulfilled and thus results in an impression event. For example, an ad campaign may run out of a pacing budget, or the same request qualifies for more than one campaigns, or the geo-block-based targeting module 3610 does not win the bidding, etc.

Pacing is a control logic that determines how an advertiser's budget should be spent relative to time so as to optimize return on investment (ROI) for the advertisers. Without pacing, the information server system would try to fulfill as many matching requests as possible, exhausting the campaign budget in the early stage of the campaign. With pacing, one or more periodic (e.g., hourly, daily, or weekly) delivery goals (budgets) are set, and the information server system 2200 uses a step-by-step methodology to create a plan to pace the fulfillment of matching requests for an information campaign so as to meet its daily and/or hourly delivery goals. Thus, an ad request matching a campaign is only fulfilled when a certain periodic goal has not been reached or a related budget has not been exhausted.

Thus, upon determining that the data units and tags in the annotated requests matches one or more information campaigns, the geo-block-based targeting module 3610 or another information server system decides whether to fulfil the request and which matching ad campaign to select to fulfill the request based on factors such as pacing, historical data about the behavior of the related mobile device (user) stored in the historical data database 2265 etc. The request is fulfilled by attaching a link to a document associated with the selected information campaign to the annotated request, and transmitting the annotated request to the mobile service provider interacting with the mobile device, e.g., mobile publishers, ad middleman, and/or ad exchanges, etc. via the network 210. The geo-block-based targeting module 3610 also monitors feedbacks indicating whether the document associated with the one or more information campaigns has been delivered to (or impressed upon) the related mobile device and provides the feedback to the real-time pacing estimation module 3630. The feedback may also be stored in the impression log in the database 2470.

At the start of an information campaign, an initial set of geographical regions or geo-blocks are provided by the geographical region scoring subsystem 2220. As the campaign proceeds in real-time, the real-time pacing estimation module 3630 periodically estimates a pacing status of the campaign based on the feedback provided by the geo-block-based targeting module 3610. The geographical region selection module 3640 compares the pacing status provided by the real-time pacing estimation module 3630 with a predetermined pacing goal for the campaign, and increases/decreases the number of geographical regions included in the targeting areas accordingly. The real-time pacing estimation module 3630 controls the dynamics of the targeting areas through, for example, the rate at which the geo-fence is updated and the minimum/maximum number of geographical regions that can be included in the geo-fence. Thus, the real-time pacing estimation module 3630 controls the balance between performance and pacing, as well as their minimum/maximum attainable values.

Thus, the information server system 2200 receives and processes information requests related to mobile users and determines whether the mobile users are potential candidates for receiving certain information services. Concurrently, the geographical region selection subsystem 2225 tracks the rate at which information related to a certain information campaign is being served to mobile users (i.e., pacing status) and adjusts the number of geo-blocks included in the targeting areas associated with the information campaign accordingly, so as to reach a balance between performance and pacing.

FIGS. 37A-37C illustrates this dynamic adjustment process according to certain embodiments. FIGS. 37A-37C are plots of geo-blocks around a point of interest 3701 represented by the small square 3701 near the center of the plots. The darker shaded geo-blocks are those included in the targeting areas associated with an information campaign at a particular time instance. Mobile device users located within these darker shaded areas at that time instance are potential candidates for receiving information service. At an earlier time instance within a first time period, as shown in FIG. 37A, only geo-blocks with performance scores above a first threshold are included in the targeting areas. From FIG. 37A to FIG. 37C, in response to the pacing status indicating that the pacing goal is not being reached, gradually more geo-blocks are included as part of the targeting areas to meet the pacing goal for the information campaign. For example, geo-block 3702 originally not included in the targeting areas as shown in FIG. 37A is now added to the targeting areas. In FIG. 37B, geo-blocks with performance scores above a second threshold lower than the first threshold are included in the targeting areas, and then later in FIG. 37C, when it is determined that more requests are needed to meet the pacing goal, geo-blocks with performance scores above a third threshold lower than the second threshold are included in the targeting areas. For example, geo-block 3703 originally not included in the targeting areas as shown in FIG. 37A or FIG. 37B is now included. Thus, by increasing the number of geo-blocks for an information campaign that is lagging behind its pacing goal(s) or by decreasing the number of geo-blocks for an information campaign that is ahead of its pacing goal(s), the campaign can be optimized to reach a balance between performance and pacing.

Several aspects of the present disclosure directly improve computer functionality. For instance, embodiments of the present disclosure achieve faster lookalike prediction with smaller memory and processing requirements by translating raw location data into location events with respect geo-fences and geo-blocks and by filtering and aggregating the location events across time and space for machine learning processes. In further embodiments, measures of relevance are computed for the geo-blocks using mobile device signals, and the measures of relevance are used to assign geo-blocks to geo-block brackets for proper dimension reduction and data clustering, resulting in efficient use of computer resources and improved location prediction performance. 

We claim:
 1. A method for discovering lookalike mobile devices, comprising: at one or more computer systems coupled to a packet-based network and including or having access to a storage unit storing therein logged request data associated with a plurality of mobile devices, the logged request data including data indicating location events triggered by the plurality of mobile devices in a predetermined time period, each location event being related to a predefined geographical place; selecting, by one or more processors of the one or more computer systems, a training set of mobile devices from the plurality of mobile devices; constructing, by one or more processors of the one or more computer systems, a respective set of features for each respective mobile device of the plurality of mobile devices, the respective set of features including location features derived from location events associated with the respective mobile devices and non-location features; determining, by one or more processors of the one or more computer systems, a label for each particular mobile device in the training set of mobile devices based at least on whether the particular mobile device is included in a seed list of mobile devices; and training, by a processor of the one or more computer systems running a machine learning program, a prediction model using the feature sets and labels for the mobile devices in the training set of mobile devices; applying, by a processor of the one or more computer systems, the prediction model to the feature sets of at least some of the plurality of mobile devices to obtain first prediction results, the first prediction results including a probability of each of the at least some of the plurality of mobile devices to be a lookalike mobile device with respect to the seed list of mobile devices.
 2. The method of claim 1, wherein the predefined geographical place is a geo-fence related to a point of interest (POI) or a geo-block corresponding to a geographical region having at least one border defined by a public road or natural boundary. 